Fixes #17436

The problem was that the upgrader only ever ran either CMS upgrades or package upgrades, this has been updated so both are run if needed.

Not that the CMS and package upgrades run in their own separate scopes, so it's safe to do it in a single notification handler 😄

Testing

Add both a CMS NoopMigration in UmbracoPlan and a package plan, unable unattended upgrades, and ensure both are run if needed.

Example package migration plan

using Umbraco.Cms.Core.Packaging;
using Umbraco.Cms.Infrastructure.Migrations;

namespace Umbraco.Cms.Web.UI;

public class MyMigrationPlan : PackageMigrationPlan
{
    public MyMigrationPlan() : base("MyPackage")
    {
    }

    protected override void DefinePlan() {
        To<NoopMigration>(Guid.Parse("AD8AF4BF-9AE1-42BC-9709-CA64891BA92D"));
    }
}